refactor(work-items): read the execution handoff modes from the vocabulary owner - #8184

Goal And Delivered Outcome

• Outcome basis / optional anchor: self-contained maintenance outcome, no issue. The accepted specification is docs/architecture/rfcs/typescript-control-plane-migration-v0.md:343, which states that new execution and configuration targets share EXECUTION_HANDOFF_MODES (soft_claim / hard_lease), with the historical HandoffMode kept for decoding.
• Goal/source and gap: loopx/control_plane/work_items/execution_preparation.ts:16 restated those two modes locally under the name HANDOFF_MODES — the exact name of the owner's three-value historical list at loopx/control_plane/coordination/handoff_mode_vocabulary.ts:2. Every other consumer of this vocabulary already imports it (local_authority_defaults.ts:6, handoff_mode_policy.ts:6, handoff_mode_migration.ts:14, work_items/task_lease_acquire.ts:1, work_items/task_lease_acquire_decision.ts:1, work_items/task_lease_lifecycle_decision.ts:1, quota/settlement_plan.ts:13, and the dashboard's apps/presentation/dashboard/src/data/chat.ts:3), so this file was the one surface holding its own copy.
• Observable before → after, with the validation row that proves it: before, the accepted handoff vocabulary existed in two places with two different names and one shadowed name; after, it exists once, and the difference between the historical and execution lists is asserted rather than implied by a local constant. See the integration and static rows.
• Issue/task and intended base: no issue is closed. Intended base main.

Author Declaration

• Written by: model_agent (Qoder Desktop coding agent, Anthropic Claude model family).

Implemented against

• Specification and revision: docs/architecture/rfcs/typescript-control-plane-migration-v0.md (and its Chinese pair, unchanged) at repository main 62e234c939996ad42f2b1168451cc9a656dce11d; the owner module's own comments, which label HANDOFF_MODES as "Shared wire vocabulary" and EXECUTION_HANDOFF_MODES as "New configuration targets".

• Self-check before submission: I read the owner module, the RFC sentence it implements, the seven existing importers, and every use of the local constant before changing it. I deliberately did not import the same-named HANDOFF_MODES list: it also contains legacy, so that "obvious" fold would silently widen the accepted handoff_mode input on this surface — the new case is written specifically to fail if anyone does that. I left LEASE_STATUSES alone; it has one definition, and folding it would be a different decision. No Python twin is claimed or moved here — the cross-runtime pair is governed by the migration RFC.

Why this is a fold and not a rename

The local list and the owner's execution list are the same two values, so the change is behaviour-preserving on every accepted input. The name, however, was not the same thing: HANDOFF_MODES in the owner carries the retired legacy mode for stored-state decoding. Binding the validator to the value-matching export instead of the name-matching one keeps the accepted set at two while removing the duplicated list, and the pinned difference is what stops a future "cleanup" from importing the wider list.

Scope And Continuation

• Completed scope and remaining work: complete within this scope. If the maintainer wants the vocabulary census extended to TypeScript module-local lists the way tests/architecture/test_content_digest_single_owner.py does for Python, that is a separate decision; this PR does not pre-empt it.
• Slice boundary / successor: N/A — independently reversible, one surface.

Validation

• Tested revision: 60c62f5f593fcc75bff23a2f5a4e1f4055531bd2
• Run state: finished
• Input classes: synthetic, public_fixture

• Coverage and gaps: the changed line is the validator input set, and the executed case drives the real projection for both accepted modes plus the rejected historical mode. The two pre-existing failures reproduce identically on an untouched base checkout of the same revision on this host; I did not investigate their causes and they are out of scope here. Gap named honestly: with the repository's dev dependencies installed the PostgreSQL integration files pass on this host, so this lane was not exercised against a live database, and the CI browser lanes and dashboard build were not run here.

Frontend / Visual Evidence

• UI impact: none
• Before: N/A
• After: N/A
• First viewport and preview: N/A
• States and viewports shown: N/A
• Source data: none
• Attention review: N/A
• Craft review: N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Refactoring (no functional changes)
• Documentation update
• Test update

LoopX Area

• Control plane (goals, todos, quota, scheduler, registry, runtime)
• Benchmark boundary (adapters, runners, verifiers, scoring, evidence)
• Capability or extension (providers, adapters, skills)
• Public docs or presentation surface (README, protocols, dashboard)
• Build, packaging, installer, or CI
• Host or runtime integration

Technical Direction

• Direction / acceptance reference, when applicable: Shared Goal Authority and cross-host coordination, under the TypeScript control-plane migration RFC.

Shared-authority RFC fixture impact

• Production-scale fixture schema: N/A — no fixture schema or generated contract changed.
• Semantic dimensions changed, or reviewed no-impact rationale: no semantic dimension moves. The accepted handoff_mode input set on this surface stays exactly soft_claim / hard_lease, which is the registered handoff_mode vocabulary's execution subset in loopx/semantics/vocabulary_v0.json.
• Provider conformance arms run: N/A
• Read-only legacy/file/PostgreSQL three-arm rehearsal: not_run — this change touches no authority store or writer fence; the PostgreSQL lanes are the pre-existing host limitation above.

Boundary Checklist

• Neither the diff nor this PR body/comments/attachments disclose private state, credentials, raw traces or verifier output, internal links, or local machine paths.
• I did not duplicate maintainer-owned benchmark work unless a maintainer split out a public issue for it.
• I kept the change scoped to the linked issue/task.
• Existing English/Chinese RFC pairs both have a diff, or no paired RFC changed: no RFC file changed.
• I completed the visual evidence section for UI changes, or marked UI impact none.
• Every commit includes a DCO Signed-off-by trailer.

Rebase note: rebased onto d0985c35aa3d05fd5de964e719aaf69f45d72535 with no content change (git patch-id --stable identical: cf8f91054e388d99a8b7); the focused lane (8 pass / 0 fail) and tsc --project tsconfig.control-plane.json --noEmit were re-run on the rebased revision.

Second rebase in this session: moved onto d0985c35aa3d05fd5de964e719aaf69f45d72535 (main advanced twice while these were open). git patch-id --stable unchanged per branch (f3ce546bc69ef120722a, 69bc07982a79a5840364, cf8f91054e388d99a8b7), and the branch's own checks were re-run on that revision: the six smoke consumers exit 0 with the change and exit 1 without it, the guard pair is 26 passed against a 3 failed, 472 passed baseline identical on the untouched base, and the TypeScript lane is 6225 tests / 2 fail against 6224 / 2 fail with the same two failing test names, tsc --noEmit clean.